View HT42B534-X_8965156.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

rev. 1.10 1 december 27, 2017 rev. 1.00 pb december 27, 2017 ht42b564-x usb (hid) to uart bridge ic usb bridge ic naming rules ht42b 5 64 -x product family ht42b = holtek bridge ic bridge series of host 5 = usb usb class type version 1 = first version bridge series of device 2 = i 2 c 3 = spi 4 = uart 3 = cdc class 6 = hid class features ? operating voltage (v dd ): 3.3v~5.5v ? uart pin voltage (v ddio ): 1.8v~v dd (less than v dd voltage) ? power down and wake-up functions to reduce power consumption ? fully integrated 12mhz oscillator with 0.25% accuracy for all usb modes which requires no external components ? usb interface ? usb 2.0 full speed compatible ? implements usb human interface device (hid) class ? internal 1.5k pull-high resistor on d+ pin ? fully-duplex universal asynchronous receiver and transmitter interface C uart ? supports baud rate up to 115200bps ? supports maximum 32 bytes transmit buffer and 32 bytes receive buffer ? uart data formats supported: C data bits: 8 C stop bits: 1 and 2 C parity: odd, even, no parity ? supports rx pin resume signal to request a remote wake-up ? supports vddio pin for uart pins power supply ? supports standard windows ? drivers for windows xp, vista, win 7, win 8/8.1, win10 ? package types: 10-pin sop general description the ht42b564-x device is a high performance usb to uart bridge controller with fully integrated usb and uart interface functions, designed for applications that communicate with various types of uart. the device includes a usb 2.0 full speed compatible interface which is used for pc communication. the device also includes a fully integrated high speed oscillator which is used as clock source for the usb and uart baud rate generator. the baud rate generator can support up to 115200bps of baud rate for the uart interface.
rev. 1.10 2 december 27, 2017 ht42b564-x selection table most features are common to all devices. the following table summarises the main features of each device. part no. description vdd usb virtual com hid fifo/buffer interface data rate i/o vdd package ht42b532-x usb to i 2 c bridge 3.3v~ 5.5v full-speed tx: 62 bytes rx: 62 bytes up to 400khz 8sop 10msop ht42b533-x usb to spi bridge tx: 128 bytes rx: 128 bytes up to 8mhz 10msop 16nsop HT42B534-X usb to uart bridge tx: 128 bytes rx: 128 bytes up to 3mbps baud 8/10sop 10msop 16nsop ht42b564-x usb (hid) to uart bridge tx: 32 bytes rx: 32 bytes up to 115.2kbps baud 10sop block diagram 3.3v regulator baud rate generator uart 32b rx buffer usb phy internal oscillator external mcu/ uart circuitry tx rx d+ d- vdd gnd ht42b564-x usb to uart bridge v33o vddio device power 32b tx buffer usb controller led udet pin assignment 10 9 8 7 6 1 2 3 4 5 v33o gnd tx vddio rx d- d+ vdd led udet ht42b564-x 10 sop-a package type marking 10sop ht42b564-x note: x=1 for version number.
rev. 1.10 3 december 27, 2017 ht42b564-x pin description pin name type description d+ i/o usb d+ line d- i/o usb d- line tx o asynchronous data output C uart transmit rx i asynchronous data input C uart receive led o tx/rx signal led indication, active low udet i usb plug-in/out detect pin v33o o 3.3v regulator output vddio pwr positive power supply for tx/rx pins vdd pwr positive power supply, usb bus power gnd pwr negative power supply, ground absolute maximum ratings supply voltage ........................... v ss -0.3v to v ss +6.0v input voltage ............................. v ss -0.3v to v dd +0.3v storage temperature .......................... -55c to 150c operating temperature ........................ -40c to 85c i oh total ........................................................... -80ma i ol total .............................................................. 80ma total power dissipation .................................. 500mw note: these are stress ratings only. stresses exceeding the range specifed under "absolute maximum ratings" may cause substantial damage to these devices. functional operation of these devices at other conditions beyond those listed in the specifcation is not implied and prolonged exposure to extreme conditions may affect devices reliability. d.c characteristics ta=25 c symbol parameter test conditions min. typ. max. unit v dd conditions v dd operating voltage 3.3 5.5 v v ddio uart pins vddio input voltage 1.8 v dd v i dd operating current 5v no load, usb plug-in 11 16 ma i sus suspend current C usb 5v suspend mode, no load, usb on, other peripherals off 360 450 a i stb standby current C non-usb 3v standby mode, no load, usb plug-out, other peripherals off, vdd power from vddio 0.1 1.0 a v il input pin input low voltage 0 0.2v ddio v v ih input pin input high voltage 0.8v ddio v ddio v i ol i/o pin sink current 3v v ol = 0.1v ddio 4 8 ma 5v 10 20 ma i oh i/o pin source current 3v v oh = 0.9v ddio -2 -4 ma 5v -5 -10 ma r ph i/o pin pull-high resistance 3v 20 60 100 k 5v 10 30 50 k i leak input leakage current 3v v in = v dd or v in = v ss 1 a 5v 1 a v v33o 3.3v regulator output voltage 5v i v33o = 70ma 3.0 3.3 3.6 v r udp1 pull-high resistance between d+ and v33o 3.3v -5% 1.5 +5% k
rev. 1.10 4 december 27, 2017 ht42b564-x a.c characteristics ta=25 c symbol parameter test condition min. typ. max. unit v dd condition f hirc high speed internal rc oscillator 3.3v~5.5v usb mode -0.25% 12 +0.25% mhz t sst system start-up timer period rx pin wake-up from power down mode 16 t hirc t rstd system reset delay time power-on reset 25 50 100 ms power-on reset characteristics ta=25 c symbol parameter test conditions min. typ. max. unit v dd conditions v por v dd start voltage to ensure power-on reset 100 mv rr por v dd rising rate to ensure power-on reset 0.035 v/ms t por minimum time for v dd stays at v por to ensure power-on reset 1 ms v dd t por rr por v por time
rev. 1.10 5 december 27, 2017 ht42b564-x usb interface the usb interface, being usb 2.0 full-speed compatible, is a 4-wire serial bus that allows communication between a host device and up to 127 max peripheral devices on the same bus. a token based protocol method is used by the host device for communication control. other advantages of the usb bus include live plugging and unplugging and dynamic device confguration. as the complexity of usb data protocol does not permit comprehensive usb operation information to be provided in this datasheet, the reader should therefore consult other external information for a detailed understanding of the usb interface. power planes there are two power planes for the device and they are the usb bus power input (vdd) and 3.3v regulator output (v33o). for the usb sie, vdd will supply all circuits related to the usb sie and be sourced from pin "vdd". once the usb device is removed from the usb bus and there is no power on the usb bus, the usb sie circuit will no longer be operational. usb interface operation to communicate with an external usb host, the internal usb module has external pins known as d+ and d- along with the 3.3v regulator output v33o. a serial interface engine, sie, decodes the incoming usb data stream and transfers it to the correct endpoint buffer memory known as the fifo. the usb module has 3 endpoints, ep0 ~ ep2. endpoint 0 supports the control transfer while endpoint 1 ~ endpoint 2 support the interrupt. the ht42b564-x bridge ic supports the usb human interface device class, hid, for communication. endpoint transfer type 0 control 1 interrupt in 2 interrupt out usb endpoint transfer type if there is no signal on the usb bus for over 3ms, the usb device will enter the suspend mode. the device enters the suspend state to meet the requirements of the usb suspend current specification. when the resume signal is asserted by the usb host, the device will be woken up and leave the suspend mode. as the usb device has a remote wake-up function, the usb device can be woken-up the usb host by sending a remote wake-up pulse. once the usb host receives a remote wake-up signal from the usb device, the host will send a resume signal to the device. usb vid and pid confguration the device has confgured the default vendor id (vid: 0x04d9), product id (pid: 0xb564) and product description strings of "usb hid uart bridge". this device has been configured to the default usb confguration data as shown in the following table. parameter value (hex) usb vendor id (vid) 0x04d9 usb product id (pid) 0xb564 remote wake-up default enable manufacturer name holtek product description usb hid uart bridge serial number 0000 usb data format read data: 32 bytes fifo for each read data, the frst byte valid for this number of data length received, ranges from 0 to 31. if there are more than 31 bytes of data, it will be divided into multiple times read. write data: 32 bytes fifo for each write data to be written first byte number, ranging from 0 to 31. if there are more than 31 bytes then write multiple times.
rev. 1.10 6 december 27, 2017 ht42b564-x uart interface the ht42b564-x contains an integrated full-duplex asynchronous serial communications uart interface that enables communication with external devices that contain a serial interface. the uart function has many features and can transmit and receive data serially by transferring a frame of data with eight data bits per transmission as well as being able to detect errors when the data is overwritten or incorrectly framed. the uart function possesses its own internal interrupt which can be used to indicate when a reception occurs or when a transmission terminates. the integrated uart function contains the following features: ? full-duplex, asynchronous communication ? 8 bits character length ? even, odd or no parity options ? one or two stop bits ? baud rate generator with prescaler ? 32-byte deep fifo transmit data buffer ? 32-byte deep fifo receive data buffer ? rx pin wake-up function ? uart pins power supply by vddio pin uart external pins to communicate with an external serial interface, the internal uart has two external pins known as tx and rx. the tx and rx pins are the uart transmitter and receiver pins respectively. uart data transfer scheme the data will be transferred to the transmit shift register from where it will be shifted out, lsb frst, onto the tx pin at a rate controlled by the baud rate generator. data to be received by the uart is accepted on the external rx pin, from where it is shifted in, lsb first, to the receiver shift register at a rate controlled by the baud rate generator. the uart interface provides a 32 byte deep fifo transmit data buffer and a 32 byte deep fifo receive data buffer for applications. for data transfer, the uart function utilises a non- return-to-zero, more commonly known as nrz, format. this is composed of one start bit, eight data bits and one or two stop bits. parity is supported by the uart hardware and can be setup to be even, odd or no parity. for the most common data format, 8 data bits along with no parity and one stop bit, denoted as 8, n, 1, is used as the default setting, which is the setting at power-on. the following diagram shows the transmit and receive waveforms for 8-bit data format. baud rate generator to setup the speed of the serial data communication, the uart function contains its own dedicated baud rate generator. the default uart baud rate is 9600bps and it can be controlled by the application program. the baud rate and miss rate table: baud rate real rate miss rate (%) 9600 9603.841537 0.04 19200 19207.68307 0.04 38400 38461.53846 0.16 57600 57692.30769 0.16 115200 115384.6154 0.16 uart power down and wake-up if the usb host sends a suspend signal to the ht42b564-x usb device, it will enter the suspend mode. it is recommended to ensure that the uart data transmission or reception has fnished before the device enters the suspend mode. the uart function contains a receiver rx pin wake- up function. a falling edge on the rx pin will wake up the device from the suspend mode. bit 0 8-bit data format bit 1 stop bit next start bit start bit parity bit bit 2 bit 3 bit 4 bit 5 bit 6 bit 7
rev. 1.10 7 december 27, 2017 ht42b564-x usb hid protocol usb vid/pid vid: 0x04d9 pid: 0xb564 usb to uart command the application program uses usb hid set/get feature command to implement uart settings. there are following command: ? get uartsetting command ? set uartsetting command (cmdcode=01) get uartsetting command request name report type raw data get_report feature d0~d7 d1~d8: uartsettings (refer to table) byte field size description d0 cmdcode 1 command code. d1~d4 dterate 4 data terminal rate,in bits per second. (support 9600/19200/38400/57600/115200) 9600 80 25 00 00 19200 00 4b 00 00 38400 00 96 00 00 57600 00 e1 00 00 115200 00 c2 01 00 d5 charfromat 1 stop bits 0-1 stop bits 1-2 stop bits d6 paritytype 1 parity 0-none 1-odd 2-even d7 databits 1 data bits(only 8) uartsettings set uartsetting command request name report type raw data set_report feature d0~d7 d0~d7: uartsettings (refer to table.1) cmdcode=01h write data request name report type raw data interrupt output d0~d31 endpoint size 32bytes the frst data of d0 is the data length. read data request name report type raw data interrupt input d0~d31 endpoint size 32bytes the frst data of d0 is the data length.
rev. 1.10 8 december 27, 2017 ht42b564-x dll function ht42b564-x usb bridge dll function holtek provides a dynamic-link library (dll) to setup the ht42b564-x bridge ic for usb to uart data communication. the dynamic-link library dll is a shared library of function executable files, available in different languages for application calls to use. the complex computing and communications usb is collated into a "hidapi.dll". users can use this dll to develop different client applications without having to spend excessive amounts of time to study and write usb related functions. dll function defnition: bool setfeature(handle hdevice, lpvoid pdata, dword nlen) ; bool getfeature (handle hdevice, lpvoid pdata, dword nlen); handle openfirsthiddevice(dword dwvid, dword dwpid, dword dwusagepage, dword dwusage, bool bsync); handle opennexthiddevice(dword dwvid, dword dwpid, dword dwusagepage, dword dwusage, bool bsync); void closehiddevice(handle hdevice); usage C taking c language as an example: ? hinstance hlib=loadlibrary ("hidapi.dll"); ? the getprocaddress function fetches the addresses for accessing various functions taking c language as an example, the declarations are as follows: bool (*setfeature)(handle hdevice, lpvoid pdata, dword nlen); bool (*getfeature)(handle hdevice, lpvoid pdata, dword nlen); handle (*openfirsthiddevice)(dword wvid, dword wpid, dword wusagepage, dword wusage, bool bsync); handle (*opennexthiddevice)(dword wvid, dword wpid, dword wusagepage, dword wusage, bool bsync); void (*closehiddevice)(handle hdevice); get the addresses (farproc&) openfirsthiddevice=getprocaddress (m_hlib,"openfirsthiddevice"); (farproc&) opennexthiddevice=getprocaddress (m_hlib,"opennexthiddevice"); (farproc&) closehiddevice=getprocaddress (m_hlib,"closehiddevice"); (farproc&) setfeature=getprocaddress (m_hlib,"setfeature"); (farproc&) getfeature=getprocaddress (m_hlib,"getfeature"); function description: handle openfirsthiddevice(dword wvid, dword wpid, dword wusagepage, dword wusage, bool bsync); handle opennexthiddevice(dword wvid, dword wpid, dword wusagepage, dword wusage,bool bsync); parameters: wvid device vendor id. any vid input will be regarded as the holtek vendor id 0x04d9 by default in this version. consult with holtek if another vid is required. wpid device product id. wusagepage/wusage the usagepage/usage adopted by the report descriptor will be written with a value of "0" if it is not specified. more detailed information is contained in the hid spec. when the same vid/pid has multiple interfaces simultaneously, it is required to specify the exact usagepage/usage, otherwise only the first interface handle value will be returned. bsync use synchronous or asynchronous transmission. synchronous transmission means that the function will not return a value until the input/output has fnished. return value: represents the value of the activated device. a null will be returned if the open operation has failed. when the same vid/pid usb devices exist simultaneously, the openfirsthiddevice function can be used to open the frst one followed by an opennexthiddevice function to open the next one until a null is returned. after activation, the device is able to execute readfile/ writefile operations, which are the windows api standard functions.
rev. 1.10 9 december 27, 2017 ht42b564-x void closehiddevice(handle hdevice); parameters: hdevice represents the value of the device to be closed. bool setfeature(handle hdevice, lpvoid pdata, dword nlen) parameters: hdevice represents the value of the activated device pdata data buffer where the feature data is to be written. the frst byte should be report id. a "0" value will be written to this byte if there is no report id. nlen length of the feature data to be written. the required length should be the firmware- defined feature report length with the addition of one report id byte. return value: 1: write success 0: write fail bool getfeature(handle hdevice, lpvoid pdata, dword nlen); return value: hdevice represents the value of the activated device pdata data buffer where the feature data is to be read. the frst byte should be report id. a "0" value will be written to this byte if there is no report id. nlen length of the feature data to be read. the required length should be the firmware-defned feature report length with the addition of one report id byte. return value: 1: read success 0: read fail considerations: ? the openfirsthiddevice/opennexthiddevice functions start up devices with a readable and writeable permission, therefore the device specifed by the vid/pid should also be readable and writable. this means that the firmware must provide outputreport/inputreport or interrupt in/ interrupt out. ? use general file access functions, such as writefile(hdevice, ) in the c language to write data to outputreport or interrupt out. the required data length should be the firmware- defined outputreport length with the addition of one report id byte. the frst byte must be the report id. it will be "0" if there is no report id. ? use general file access functions, such as readfile(hdevice, ) in the c language, to read data from inputreport or interrupt in. the required data length should be the firmware-defined inputreport length with the addition of one report id byte. the first byte must be the report id. it will be "0" if there is no report id. ? to use the setfeature/getfeature functions, the device must provide feature report, which means the report descriptor of the firmware should contain the feature type.
rev. 1.10 10 december 27, 2017 ht42b564-x application circuits vdd gnd v33o d- d+ vddio 1f vbus d- d+ vss 0.1f 10f 47pf 47pf 33 ? 33 ? 0.1f vdd mcu application circuit ht42b564-x 10 sop-a usb connector 3.3v bat tx rx udet led vcc 1n5817 5v or 3.3v 3.3v 0.1f vdd 330 ? led tx rx uart note: 1. t he v cc voltage must be less than the v voltage. the v cc supply can be sourced from a li-battery. 2. the udet pin can used to detect a usb plug-in for data transfer or to detect a usb plug-out for entering the energy saving mode.
rev. 1.10 11 december 27, 2017 ht42b564-x package information note that the package information provided here is for consultation purposes only. as this information may be updated at regular intervals users are reminded to consult the holtek website for the latest version of the package/ carton information . additional supplementary information with regard to packaging is listed below. click on the relevant section to be transferred to the relevant website page. ? further package information (include outline dimensions, product tape and reel specifcations) ? packing meterials information ? carton information
rev. 1.10 12 december 27, 2017 ht42b564-x 10-pin sop (150mil) outline dimensions symbol dimensions in inch min. nom. max. a 0.236 bsc b 0.154 bsc c 0.012 0.018 c 0.193 bsc d 0.069 e 0.039 bsc f 0.004 0.010 g 0.016 0.050 h 0.004 0.010 0 8 symbol dimensions in mm min. nom. max. a 6.00 bsc b 3.90 bsc c 0.30 0.45 c 4.90 bsc d 1.75 e 1.00 bsc f 0.10 0.25 g 0.40 1.27 h 0.10 0.25 0 8
rev. 1.10 13 december 27, 2017 ht42b564-x copyright ? 2016 by holtek semiconductor inc. the information appearing in this data sheet is believed to be accurate at the time of publication. however, holtek assumes no responsibility arising from the use of the specifcations described. the applications mentioned herein are used solely for the purpose of illustration and holtek makes no warranty or representation that such applications will be suitable without further modification, nor recommends the use of its products for application that may present a risk to human life due to malfunction or otherwise. holtek's products are not authorized for use as critical components in life support devices or systems. holtek reserves the right to alter its products without prior notifcation. for the most up-to-date information, please visit our web site at http://www.holtek.com.tw/en/home.

▲Up To Search▲

Price & Availability of HT42B534-X

	To Download HT42B534-X Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .